Configuring SBC IP-to-IP Routing Rules

Assigns a Routing Policy to the rule. The Routing Policy associates the rule with an SRD(s). The Routing Policy also defines default LCR settings as well as the LDAP servers used if the routing rule is based on LDAP routing (and Call Setup Rules).

If only one Routing Policy is configured in the Routing Policies table, the Routing Policy is automatically assigned. If multiple Routing Policies are configured, no value is assigned.

To configure Routing Policies, see Configuring SBC Routing Policies.

Note: The parameter is mandatory.

Defines an index number for the new table row.

Note: Each row must be configured with a unique index.

Defines a descriptive name, which is used when associating the row in other tables.

The valid value is a string of up to 40 characters. By default, no value is defined.

Note: The parameter value can't be configured with the character string "any" (upper or lower case).

Determines whether this routing rule is the main routing rule or an alternative routing rule (to the rule defined directly above it in the table).

Note:

Defines the IP Group from where the IP call is received (i.e., the IP Group that sent the SIP dialog). Typically, the IP Group of an incoming SIP dialog is determined (or classified) using the Classification table (see Configuring Classification Rules).

The default is Any (i.e., any IP Group).

Note: The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table). For more information, see Configuring SBC Routing Policy Rules.

Defines the SIP dialog request type (SIP Method) of the incoming SIP dialog.

Note:

Defines the user part of the incoming SIP dialog's source URI (usually the From URI).

You can use special patterns (notations) to denote the user part. For example, if you want to match this rule to user parts whose last four digits (i.e., suffix) are 4 followed by any three digits (e.g., 4008), then configure this parameter to "(4xxx)". To denote calls without a user part in the URI, use the dollar ($) sign. For available patterns, see Dialing Plan Notation for Routing and Manipulation.

The valid value is a string of up to 60 characters. The default is the asterisk (*) symbol (i.e., any user part).

If this rule is not required, leave this field empty.

Note: If you need to route calls of many different source URI user names to the same destination, you can use tags (see 'Source Tags' parameter below) instead of this parameter.

Defines the host part of the incoming SIP dialog's source URI (usually the From URI).

The default is the asterisk (*) symbol (i.e., any host name). If this rule is not required, leave this field empty.

Defines a source tag(s) for matching this routing rule.

The source tag can be obtained using a Dial Plan (assigned to the source IP Group or SRD) or Call Setup Rules (assigned to the source IP Group or SIP Interface).

The valid value is:

By default, no value is defined.

The following example configures the maximum number of tags (i.e., seven name=value tags and one value-only tag): Country=Ireland;Country2=Scotland;Country3=RSA;Country4=Canada;Country5=UK;Country6=France;Country7=Germany;USA.

To configure Dial Plans, see Configuring Dial Plans. To configure tags using Call Setup Rules (i.e., using the SrcTags attribute), see Configuring Call Setup Rules.

Note:

Defines the incoming SIP dialog's destination URI (usually the Request URI) user part.

You can use special patterns (notations) to denote the user part. For example, if you want to match this rule to user parts whose last four digits (i.e., suffix) are 4 followed by any three digits (e.g., 4008), then configure this parameter to "(4xxx)". To denote calls without a user part in the URI, use the dollar ($) sign. For available patterns, see Dialing Plan Notation for Routing and Manipulation.

The valid value is a string of up to 60 characters. The default is the asterisk (*) symbol (i.e., any user part). If this rule is not required, leave this field empty.

Note: If you need to route calls of many different destination URI user names to the same destination, you can use tags (see 'Source Tags' parameter below) instead of this parameter.

Defines the host part of the incoming SIP dialog’s destination URI (usually the Request-URI).

The default is the asterisk (*) symbol (i.e., any destination host). If this rule is not required, leave this field empty.

Defines a destination tag(s) for matching this routing rule.

The destination tag can be obtained using a Dial Plan (assigned to the source IP Group or SRD) or Call Setup Rules (assigned to the source IP Group or SIP Interface).

The valid value is:

By default, no value is defined.

The following example configures the maximum number of tags (i.e., seven name=value tags and one value-only tag): Country=Ireland;Country2=Scotland;Country3=RSA;Country4=Canada;Country5=UK;Country6=France;Country7=Germany;USA.

To configure Dial Plans, see Configuring Dial Plans. To configure tags using Call Setup Rules (i.e., using the DstTags attribute), see Configuring Call Setup Rules.

Note:

Assigns a SIP Message Condition rule to the IP-to-IP Routing rule.

To configure Message Condition rules, see Configuring Message Condition Rules.

Defines the reason (i.e., trigger) for re-routing (i.e., alternative routing) the SIP request.

Defines the IP Group that initiated (sent) the SIP redirect response (e.g., 3xx) or REFER message. This parameter is typically used for rerouting requests (e.g., INVITEs) when interworking is required for SIP 3xx redirect responses or REFER messages. For more information, see Interworking SIP 3xx Redirect Responses and Interworking SIP REFER Messages, respectively. The parameter functions together with the 'Call Trigger' parameter (in the table).

The default is Any (i.e., any IP Group).

Note: The selectable IP Group for the parameter depends on the assigned Routing Policy (in the 'Routing Policy' parameter in this table). For more information, see Configuring SBC Routing Policy Rules.

Defines the type of destination to where the device sends the outgoing SIP dialog.

Note that the second parameter "0" is ignored. An example of a configured Dial Plan (# 6) in the Dial Plan file is shown below:

[ PLAN6 ]
200,0,10.33.8.52     ; called prefix 200 is routed to destination 10.33.8.52
201,0,10.33.8.52
300,0,itsp.com       ; called prefix 300 is routed to destination itsp.com

Once the Dial Plan is defined, you need to assign it (0 to 7) to the routing rule as the destination in the 'Destination Address' parameter, where "0" denotes [PLAN1], "1" denotes [PLAN2], and so on.

Note:

If the incoming SIP dialog is a REGISTER message, the device acts as a registrar and only responds to the sender of the request (200 OK) without sending the REGISTER message to a destination (i.e., termination of REGISTER messages).

Note: For tag-based routing, you also need to configure the 'Routing Tag Name' parameter (below).

Note:

Defines the IP Group to where you want to route the call. The actual destination of the SIP dialog message depends on the IP Group type (as defined in the 'Type' parameter):

By default, no value is defined.

Note:

Defines the destination SIP Interface to where the call is sent.

By default, no value is defined.

To configure SIP Interfaces, see Configuring SIP Interfaces.

Note:

Defines the destination address to where the call is sent.

The valid value is an IP address in dotted-decimal notation or an FQDN (domain name, e.g., domain.com).

If ENUM-based routing is used (i.e., the 'Destination Type' parameter is set to ENUM) the parameter configures the address of the ENUM service, for example, e164.arpa, e164.customer.net or NRENum.net. The device sends the ENUM query containing the destination phone number to an external DNS server, configured in the IP Interfaces table. The ENUM reply includes a SIP URI (user@host) which is used as the destination Request-URI in this routing table.

The valid value is a string of up to 50 characters (IP address or FQDN). By default, no value is defined.

Note:

Defines the destination port to where the call is sent.

Defines the transport layer type for sending the call.

Assigns an IP Group Set to the routing rule. The device routes the call to one of the IP Groups in the IP Group Set according to the load-balancing policy configured for the IP Group Set. For more information, see Configuring IP Group Sets.

Note: The parameter is applicable only if you configure the 'Destination Type' parameter to IP Group Set (above).

Assigns a Call Setup Rule Set ID to the routing rule. The device runs this Call Setup Rules Set if the incoming call matches the characteristics of this routing rule. The device routes the call to the destination according to the routing rule's configured action, only after it has run the Call Setup rules.

To configure Call Setup rules, see Configuring Call Setup Rules.

Note:

Assigns a Call Setup Rule Set ID to the routing rule. The device runs the Call Setup rules of this Set ID if the incoming call matches the characteristics of this routing rule. The device routes the call to the destination according to the routing rule's configured action, only after it has run the Call Setup rules.

To configure Call Setup rules, see Configuring Call Setup Rules.

Note:

Defines if the routing rule includes call forking.

Note: Each Forking Group can contain up to 20 members. In other words, up to 20 routing rules can be configured for the same Forking Group.

Assigns a Cost Group to the routing rule for determining the cost of the call.

By default, no value is defined.

To configure Cost Groups, see Configuring Cost Groups.

Note:

Defines the destination tag name, which is used to determine the destination IP Group. The device searches the IP Groups table for an IP Group whose 'Tags' parameter value matches this tag name (and value).

The valid value:

The default value is "default", meaning that the device uses the first tag name that is configured without a value. For example, if the Dial Plan rule is configured with tags "Country=England;City=London;Essex", the default tag is "Essex".

An example of configuring this parameter when Call Setup Rules (assigned to the 'Pre Route Call Setup Rules Set ID' parameter above) are used to obtain the tag name: If you configure the parameter to "IPGroupName" (i.e., tag name) and the Call Setup Rule's 'Action Subject' parameter is "DstTags.IPGroupName" which results in the value “Teams” (i.e., tag value), the device searches the IP Groups table for a destination IP Group whose 'Tags' parameter is configured to "ipGroupName=Teams".

For more information on tag-based routing, see Using Destination Tags for Choosing Routing Destinations.

Note:

Defines a SIP response code (e.g., 200 OK) or a redirection response (with an optional Contact field indicating to where the sender must re-send the message) that the device sends to the sender of the incoming SIP dialog (instead of sending the call to another destination). The parameter is applicable only when the 'Destination Type' parameter in this table is configured to Internal (see above).

The valid value syntax (case-insensitive) is:

reply(response='<code>') 

The following example sends a SIP 200:

reply(response='200')

redirect(response='<code>',contact='sip:'+….)

redirect(contact='…',response='<code>')

redirect(contact='sip:user@host')

Examples:

redirect(response=’300’,contact=’sip:102@host’)

redirect(response='302',contact='sip:'+header.to.url.user+'@siprecording.com')

You can use the built-in syntax editor to help you configure the field. Click the Editor button located alongside the field to open the Editor, and then simply follow the on-screen instructions.

Note: